home *** CD-ROM | disk | FTP | other *** search
- RESIDENT
-
- Displays and modifies the list of resident commands.
-
- Format
-
- RESIDENT [<resident name>] [<filename>] [REMOVE] [ADD] [REPLACE] [PURE |
- FORCE] [SYSTEM]
-
- Template
-
- NAME,FILE,REMOVE/S,ADD/S,REPLACE/S,PURE=FORCE/S,SYSTEM/S
-
- Location
-
- Internal
-
- RESIDENT loads a command into memory and adds it to the resident list
- maintained by the Shell. This allows the command to be executed without
- reloading it from disk each time. If RESIDENT is invoked with no options, it
- lists the programs on the resident list.
-
- To be made resident, a command should be pure, meaning that it is both
- re-entrant and re-executable. A re-entrant command can properly support
- independent use by two or more programs at the same time. A re-executable
- command dies not have to be reloaded to be executed again. Commands that have
- these characteristics are called pure and have the p (pure) protection bit
- set.
-
- The following commands cannot be made resident: BINDDRIVERS, CONCLIP, IPREFS,
- LOADRESOURCE, LOADWB, and SETPATCH.
-
- LIST the C: directory to check for the presence of the p protection bit to
- determine which commands are pure.
-
- Many of the commands in the C: directory, as well as the MORE command in
- Utilities, are pure commands and can be made resident. If a command does not
- have its pure bit set, it probably cannot be made resident safely. (Setting
- the pure bit does not make a command or program pure.)
-
- The REPLACE option is the default option and does not need to be explicitly
- stated. If no <resident name> is specified (for example, only a file name is
- specified), RESIDENT uses the file name portion as the name on the resident
- list. The full path to the file must be used.
-
- If a <resident name> is specified and RESIDENT finds a program with that name
- already on the list, it attempts to replace the command. That <resident name>
- must be used to reference the resident version of the command. The
- replacement succeeds only if the already-resident command is not in use.
-
- To override REPLACEment and make several versions of a command resident
- simultaneously, use the ADD option, giving a different <resident name> for
- each version loaded.
-
- If the System option is specified, the command is added to the system portion
- of the resident list and becomes available as a system component. Any
- commands added to the resident list with the SYSTEM option cannot be removed.
- To list these files on the RESIDENT list, you must specify the SYSTEM option.
-
- The PURE option forces RESIDENT to load commands that are not marked as pure
- and use them to test the pureness of other commands and programs. Use the
- PURE option with caution. Be sure the programs that you make RESIDENT meet
- the criteria to be resident or be careful to use the command in only one
- process at a time.
-
- The availability of internal commands can also be controlled with RESIDENT.
- To deactivate an Internal command (for example, if an application has its own
- command of the same name), use RESIDENT <command> REMOVE. The command can be
- reactivated with the REPLACE option.
-
- Example 1:
-
- 1> RESIDENT C:COPY
-
- makes the COPY command resident (replaces any previous version).
-
- Example 2:
-
- 1> RESIDENT Copy2 DF1:C/COPY ADD
-
- adds another version of COPY to the resident list, under the name Copy2.
-
- Example 3:
-
- 1> RESIDENT Xdir DF1:C/Xdir PURE
-
- makes an experimental, non-pure version of the DIR command resident.
-
- Example 4:
-
- 1> RESIDENT CD REMOVE
-
- makes the Internal CD command unavailable.
-
- Example 5:
-
- 1> RESIDENT CD REPLACE
-
- restores the CD command to the system.
-
- See also: PROTECT, LIST.
-